At 9:40 PM +0400 4/19/05, Alexandre wrote:
>Lane, thank you, but it is not: PostISAM "generates SQL statements
>on the fly from traditional ISAM (read, write, start) statements",
>so it just add overhead, and is not what I'm looking for.
Speaking from experience, as I have a system which hides Postgres
behind an ISAM interface (though not PostISAM -- I rolled my own DB
library) as part of a legacy 4GL migration, the overhead's ignorable.
Dismissing it for that reason's not a good idea.
>On Apr 19, 2005, at 18:16, Tom Lane wrote:
>
>>Alexandre <Xlex0x835@rambler.ru> writes:
>>>What I mean is: currently to get/put/delete/edit any data I have to
>>>compose an SQL query, which should be parsed, compiled, optimized and
>>>so on. While, in some tasks simple interface a-la [G|N]DBM should be
>>>more than enough, but it will be more preferable to store all data in
>>>one database, which support concurrent access, transactions, etc.
>>
>>I seem to recall that someone has written an ISAM-style interface
>>library, which might be more or less what you are asking for. Check
>>the archives, and/or look at gborg and pgfoundry.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
dan@sidhe.org have teddy bears and even
teddy bears get drunk
